Skip to content

[VS test] Increase test timeout#1988

Merged
theasianpianist merged 1 commit intosonic-net:masterfrom
prsunny:timout
Oct 27, 2021
Merged

[VS test] Increase test timeout#1988
theasianpianist merged 1 commit intosonic-net:masterfrom
prsunny:timout

Conversation

@prsunny
Copy link
Copy Markdown
Collaborator

@prsunny prsunny commented Oct 26, 2021

What I did
Increase test timeout to 240mts from 180mts

Why I did it

Started observing the following error:

##[error]The job running on agent Azure Pipelines 5 ran longer than the maximum time of 180 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134

How I verified it

Details if related

Failure link here

@theasianpianist theasianpianist merged commit ac09bde into sonic-net:master Oct 27, 2021
@prsunny prsunny deleted the timout branch October 28, 2021 17:59
EdenGri pushed a commit to EdenGri/sonic-swss that referenced this pull request Feb 28, 2022
…nic-net#1988)

#### What I did
Fixes sonic-net#1976

Different runs of `apply-patch` would produce different sorted steps. It is better to be consistent while producing the sorted steps to make it easier to debug issues in the future.

The issue is with using `set(list)` to remove duplicates from the list. Looping over the set elements does not guarantee same order every time we iterate. To reproduce this do the following:
1. Create a file named `test.py` with the content
```python
x = ["XYZ", "ABC", "DEF"]
y = set(x)
print(y)
```
2. Run `python3 test.py`
3. Again `python3 test.py`
4. Again `python3 test.py`
The output of these runs will be different each time.

#### How I did it
Instead of returning a `set`, return a list of `ref_paths` which does not have duplicated elements inserted to begin with.

#### How to verify it
unit-tests

#### Previous command output (if the output of a command-line utility has changed)

#### New command output (if the output of a command-line utility has changed)
Janetxxx pushed a commit to Janetxxx/sonic-swss that referenced this pull request Nov 10, 2025
Workaround for some tests timing out at 99% completion
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants