-
Notifications
You must be signed in to change notification settings - Fork 356
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: update log viewer to load older logs when near the top [DET-3557] #879
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… top is close enough
hkang1
changed the title
feat: update log viewer to load older logs when near the top
feat: update log viewer to load older logs when near the top [DET-3557]
Jul 14, 2020
armandmcqueen
approved these changes
Jul 20, 2020
eecsliu
pushed a commit
to eecsliu/determined
that referenced
this pull request
Jun 23, 2023
Migrate the test-e2e-slurm from running on znode to running on gcp. For each circle-ci job it creates a devbox that runs the test cases for e2e_slurm. This allows multiple users to run the jobs at the same time since each devbox is unique. Acceptance Criteria The test-e2e-slurm suite content at gate runs on gcp instead of znode* as suite test-e2e-slurm-singularity-gcp The current test-e2e-slurm suite instead runs only nightly on znode (could be renamed to test-e2e-slurm-znode) Multiple users can run it at the same time without conflicting (currently I believe there is a single circleci-gcp-dev-box VM)
eecsliu
pushed a commit
that referenced
this pull request
Jun 28, 2023
Migrate the test-e2e-slurm from running on znode to running on gcp. For each circle-ci job it creates a devbox that runs the test cases for e2e_slurm. This allows multiple users to run the jobs at the same time since each devbox is unique. Acceptance Criteria The test-e2e-slurm suite content at gate runs on gcp instead of znode* as suite test-e2e-slurm-singularity-gcp The current test-e2e-slurm suite instead runs only nightly on znode (could be renamed to test-e2e-slurm-znode) Multiple users can run it at the same time without conflicting (currently I believe there is a single circleci-gcp-dev-box VM)
eecsliu
pushed a commit
that referenced
this pull request
Jun 28, 2023
Migrate the test-e2e-slurm from running on znode to running on gcp. For each circle-ci job it creates a devbox that runs the test cases for e2e_slurm. This allows multiple users to run the jobs at the same time since each devbox is unique. Acceptance Criteria The test-e2e-slurm suite content at gate runs on gcp instead of znode* as suite test-e2e-slurm-singularity-gcp The current test-e2e-slurm suite instead runs only nightly on znode (could be renamed to test-e2e-slurm-znode) Multiple users can run it at the same time without conflicting (currently I believe there is a single circleci-gcp-dev-box VM)
stoksc
pushed a commit
that referenced
this pull request
Jul 20, 2023
Migrate the test-e2e-slurm from running on znode to running on gcp. For each circle-ci job it creates a devbox that runs the test cases for e2e_slurm. This allows multiple users to run the jobs at the same time since each devbox is unique. Acceptance Criteria The test-e2e-slurm suite content at gate runs on gcp instead of znode* as suite test-e2e-slurm-singularity-gcp The current test-e2e-slurm suite instead runs only nightly on znode (could be renamed to test-e2e-slurm-znode) Multiple users can run it at the same time without conflicting (currently I believe there is a single circleci-gcp-dev-box VM)
eecsliu
pushed a commit
that referenced
this pull request
Jul 24, 2023
Migrate the test-e2e-slurm from running on znode to running on gcp. For each circle-ci job it creates a devbox that runs the test cases for e2e_slurm. This allows multiple users to run the jobs at the same time since each devbox is unique. Acceptance Criteria The test-e2e-slurm suite content at gate runs on gcp instead of znode* as suite test-e2e-slurm-singularity-gcp The current test-e2e-slurm suite instead runs only nightly on znode (could be renamed to test-e2e-slurm-znode) Multiple users can run it at the same time without conflicting (currently I believe there is a single circleci-gcp-dev-box VM)
rb-determined-ai
pushed a commit
that referenced
this pull request
Oct 5, 2023
Migrate the test-e2e-slurm from running on znode to running on gcp. For each circle-ci job it creates a devbox that runs the test cases for e2e_slurm. This allows multiple users to run the jobs at the same time since each devbox is unique. Acceptance Criteria The test-e2e-slurm suite content at gate runs on gcp instead of znode* as suite test-e2e-slurm-singularity-gcp The current test-e2e-slurm suite instead runs only nightly on znode (could be renamed to test-e2e-slurm-znode) [e2e_tests changes only]
rb-determined-ai
pushed a commit
that referenced
this pull request
Oct 10, 2023
Migrate the test-e2e-slurm from running on znode to running on gcp. For each circle-ci job it creates a devbox that runs the test cases for e2e_slurm. This allows multiple users to run the jobs at the same time since each devbox is unique. Acceptance Criteria The test-e2e-slurm suite content at gate runs on gcp instead of znode* as suite test-e2e-slurm-singularity-gcp The current test-e2e-slurm suite instead runs only nightly on znode (could be renamed to test-e2e-slurm-znode) [e2e_tests changes only]
stoksc
pushed a commit
that referenced
this pull request
Oct 17, 2023
Migrate the test-e2e-slurm from running on znode to running on gcp. For each circle-ci job it creates a devbox that runs the test cases for e2e_slurm. This allows multiple users to run the jobs at the same time since each devbox is unique. Acceptance Criteria The test-e2e-slurm suite content at gate runs on gcp instead of znode* as suite test-e2e-slurm-singularity-gcp The current test-e2e-slurm suite instead runs only nightly on znode (could be renamed to test-e2e-slurm-znode) Multiple users can run it at the same time without conflicting (currently I believe there is a single circleci-gcp-dev-box VM)
rb-determined-ai
pushed a commit
that referenced
this pull request
Oct 27, 2023
Migrate the test-e2e-slurm from running on znode to running on gcp. For each circle-ci job it creates a devbox that runs the test cases for e2e_slurm. This allows multiple users to run the jobs at the same time since each devbox is unique. Acceptance Criteria The test-e2e-slurm suite content at gate runs on gcp instead of znode* as suite test-e2e-slurm-singularity-gcp The current test-e2e-slurm suite instead runs only nightly on znode (could be renamed to test-e2e-slurm-znode) [e2e_tests changes only]
rb-determined-ai
pushed a commit
that referenced
this pull request
Oct 31, 2023
Migrate the test-e2e-slurm from running on znode to running on gcp. For each circle-ci job it creates a devbox that runs the test cases for e2e_slurm. This allows multiple users to run the jobs at the same time since each devbox is unique. Acceptance Criteria The test-e2e-slurm suite content at gate runs on gcp instead of znode* as suite test-e2e-slurm-singularity-gcp The current test-e2e-slurm suite instead runs only nightly on znode (could be renamed to test-e2e-slurm-znode) [e2e_tests changes only]
rb-determined-ai
pushed a commit
that referenced
this pull request
Nov 2, 2023
Migrate the test-e2e-slurm from running on znode to running on gcp. For each circle-ci job it creates a devbox that runs the test cases for e2e_slurm. This allows multiple users to run the jobs at the same time since each devbox is unique. Acceptance Criteria The test-e2e-slurm suite content at gate runs on gcp instead of znode* as suite test-e2e-slurm-singularity-gcp The current test-e2e-slurm suite instead runs only nightly on znode (could be renamed to test-e2e-slurm-znode) [e2e_tests changes only]
rb-determined-ai
pushed a commit
that referenced
this pull request
Nov 2, 2023
Migrate the test-e2e-slurm from running on znode to running on gcp. For each circle-ci job it creates a devbox that runs the test cases for e2e_slurm. This allows multiple users to run the jobs at the same time since each devbox is unique. Acceptance Criteria The test-e2e-slurm suite content at gate runs on gcp instead of znode* as suite test-e2e-slurm-singularity-gcp The current test-e2e-slurm suite instead runs only nightly on znode (could be renamed to test-e2e-slurm-znode) [e2e_tests changes only]
azhou-determined
pushed a commit
that referenced
this pull request
Dec 7, 2023
Migrate the test-e2e-slurm from running on znode to running on gcp. For each circle-ci job it creates a devbox that runs the test cases for e2e_slurm. This allows multiple users to run the jobs at the same time since each devbox is unique. Acceptance Criteria The test-e2e-slurm suite content at gate runs on gcp instead of znode* as suite test-e2e-slurm-singularity-gcp The current test-e2e-slurm suite instead runs only nightly on znode (could be renamed to test-e2e-slurm-znode) [excluding e2e_tests changes]
wes-turner
pushed a commit
that referenced
this pull request
Feb 2, 2024
Migrate the test-e2e-slurm from running on znode to running on gcp. For each circle-ci job it creates a devbox that runs the test cases for e2e_slurm. This allows multiple users to run the jobs at the same time since each devbox is unique. Acceptance Criteria The test-e2e-slurm suite content at gate runs on gcp instead of znode* as suite test-e2e-slurm-singularity-gcp The current test-e2e-slurm suite instead runs only nightly on znode (could be renamed to test-e2e-slurm-znode) [excluding e2e_tests changes]
rb-determined-ai
pushed a commit
that referenced
this pull request
Feb 29, 2024
Migrate the test-e2e-slurm from running on znode to running on gcp. For each circle-ci job it creates a devbox that runs the test cases for e2e_slurm. This allows multiple users to run the jobs at the same time since each devbox is unique. Acceptance Criteria The test-e2e-slurm suite content at gate runs on gcp instead of znode* as suite test-e2e-slurm-singularity-gcp The current test-e2e-slurm suite instead runs only nightly on znode (could be renamed to test-e2e-slurm-znode) [excluding e2e_tests changes]
amandavialva01
pushed a commit
that referenced
this pull request
Mar 18, 2024
Migrate the test-e2e-slurm from running on znode to running on gcp. For each circle-ci job it creates a devbox that runs the test cases for e2e_slurm. This allows multiple users to run the jobs at the same time since each devbox is unique. Acceptance Criteria The test-e2e-slurm suite content at gate runs on gcp instead of znode* as suite test-e2e-slurm-singularity-gcp The current test-e2e-slurm suite instead runs only nightly on znode (could be renamed to test-e2e-slurm-znode) [excluding e2e_tests changes]
eecsliu
pushed a commit
that referenced
this pull request
Apr 18, 2024
Migrate the test-e2e-slurm from running on znode to running on gcp. For each circle-ci job it creates a devbox that runs the test cases for e2e_slurm. This allows multiple users to run the jobs at the same time since each devbox is unique. Acceptance Criteria The test-e2e-slurm suite content at gate runs on gcp instead of znode* as suite test-e2e-slurm-singularity-gcp The current test-e2e-slurm suite instead runs only nightly on znode (could be renamed to test-e2e-slurm-znode) [excluding e2e_tests changes]
eecsliu
pushed a commit
to determined-ai/determined-release-testing
that referenced
this pull request
Apr 22, 2024
Migrate the test-e2e-slurm from running on znode to running on gcp. For each circle-ci job it creates a devbox that runs the test cases for e2e_slurm. This allows multiple users to run the jobs at the same time since each devbox is unique. Acceptance Criteria The test-e2e-slurm suite content at gate runs on gcp instead of znode* as suite test-e2e-slurm-singularity-gcp The current test-e2e-slurm suite instead runs only nightly on znode (could be renamed to test-e2e-slurm-znode) [excluding e2e_tests changes]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Triggers when approximately within 50 pixels of the top of the scroll position.
Test Plan
Commentary (optional)