Fix browser profile launch by specifying relative path inside oid dir to profilejob #2912
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.
Fixes #2911
Follow-up to #2891
This commit strips the oid prefix from the profile filename before passing it along to the profilejob so that it's in the format the crawler expects.
I've also added a profile to an existing test that runs a crawl and verifies that state is
completeat finished (i.e. not failed) to catch any similar type regression in the future.Testing
python -m pytest backend/test_nightly/test_crawl_not_logged_in.py