nomad-FAIR issueshttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues2023-02-16T13:27:45Zhttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1343Issue: unavailable persistent volume claim of north tools in the staging depl...2023-02-16T13:27:45ZAdam FeketeIssue: unavailable persistent volume claim of north tools in the staging deploymentAdam FeketeAdam Feketehttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1247K8s doesn't work due to the missing rabbitmq chart2022-12-20T15:06:25ZAdam FeketeK8s doesn't work due to the missing rabbitmq chartThe version (8.30.1) of the rabbitmq chart is not available anymore:
```
Error: can't get a valid version for repositories rabbitmq. Try changing the version constraint in Chart.yaml
```
list of available versions:
```bash
$ helm search...The version (8.30.1) of the rabbitmq chart is not available anymore:
```
Error: can't get a valid version for repositories rabbitmq. Try changing the version constraint in Chart.yaml
```
list of available versions:
```bash
$ helm search repo rabbitmq/rabbitmq -l
NAME CHART VERSION APP VERSION DESCRIPTION
rabbitmq/rabbitmq 11.2.2 3.11.5 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 11.2.1 3.11.5 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 11.2.0 3.11.4 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 11.1.5 3.11.4 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 11.1.4 3.11.3 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 11.1.3 3.11.3 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 11.1.2 3.11.3 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 11.1.1 3.11.2 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 11.1.0 3.11.2 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 11.0.4 3.11.2 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 11.0.3 3.11.2 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 11.0.2 3.11.1 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 11.0.1 3.11.1 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 11.0.0 3.11.0 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.3.9 3.10.8 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.3.8 3.10.8 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.3.7 3.10.8 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.3.6 3.10.8 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.3.5 3.10.7 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.3.4 3.10.7 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.3.3 3.10.7 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.3.2 3.10.7 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.3.1 3.10.7 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.3.0 3.10.7 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.2.1 3.10.7 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.2.0 3.10.7 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.1.19 3.10.7 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.1.18 3.10.7 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.1.17 3.10.7 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.1.16 3.10.6 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.1.15 3.10.6 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.1.14 3.10.5 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.1.13 3.10.5 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.1.12 3.10.5 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.1.11 3.10.5 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.1.10 3.10.5 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.1.9 3.10.5 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.1.8 3.10.5 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.1.7 3.10.5 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.1.6 3.10.5 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.1.5 3.10.5 RabbitMQ is an open source general-purpose mess...
rabbitmq/rabbitmq 10.1.4 3.10.5 RabbitMQ is an open source general-purpose mess...
```https://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1220Keycloak redirect problem with nomad-oasis behind ssl (traefik) proxy2023-12-21T15:38:48ZAdam FeketeKeycloak redirect problem with nomad-oasis behind ssl (traefik) proxyThe url returns with "502 Bad gateway nginx/1.13.9"
```
https://nomad.eln.data.fau.de/keycloak/auth/realms/nomad/protocol/openid-connect/auth?response_type=code&redirect_uri=http%3A%2F%2Fnomad.eln.data.fau.de%2Fnomad-oasis%2Fnorth%2Fhub%...The url returns with "502 Bad gateway nginx/1.13.9"
```
https://nomad.eln.data.fau.de/keycloak/auth/realms/nomad/protocol/openid-connect/auth?response_type=code&redirect_uri=http%3A%2F%2Fnomad.eln.data.fau.de%2Fnomad-oasis%2Fnorth%2Fhub%2Foauth_callback&client_id=nomad_public&state=eyJzdGF0ZV9pZCI6ICJmOTMxYWIyMWM3NDU0MWUwYTRkNzczYTVmZDU1Y2FiNCIsICJuZXh0X3VybCI6ICIvbm9tYWQtb2FzaXMvbm9ydGgvaHViL2FwaS9vYXV0aDIvYXV0aG9yaXplP2NsaWVudF9pZD1qdXB5dGVyaHViLXVzZXItYWRtaW4tanVweXRlciZyZWRpcmVjdF91cmk9JTJGbm9tYWQtb2FzaXMlMkZub3J0aCUyRnVzZXIlMkZhZG1pbiUyRmp1cHl0ZXIlMkZvYXV0aF9jYWxsYmFjayZyZXNwb25zZV90eXBlPWNvZGUmc3RhdGU9ZXlKMWRXbGtJam9nSW1VME9EVTJOVFU0WkRrNFpUUXhOemc0TkRWaVltUTVNamt6TXpCallXTXlJaXdnSW01bGVIUmZkWEpzSWpvZ0lpOXViMjFoWkMxdllYTnBjeTl1YjNKMGFDOTFjMlZ5TDJGa2JXbHVMMnAxY0hsMFpYSXZkSEpsWlNKOSJ9&scope=openid+profile
```Adam FeketeAdam Feketehttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/905Kubernetes: switching to namespaces instead of using prefixes2022-12-10T00:44:47ZAdam FeketeKubernetes: switching to namespaces instead of using prefixesThe goal is to use namespaces to separate all the dev deployments from each other. Right now there is a single `nomad` namespace and all the pods/services are using a prefix to avoid any conflict.
Benefits:
- slightly more reasonable te...The goal is to use namespaces to separate all the dev deployments from each other. Right now there is a single `nomad` namespace and all the pods/services are using a prefix to avoid any conflict.
Benefits:
- slightly more reasonable testing environment
- different deployments cannot affect each other
- simplified pod/service names
- possibility to use the same release name
- in the case of a single namespace the explosion of the Pod Information to Containers Through Environment Variables could be dangerous
Disadvantage:
- the explosion of namespaces (cleanup is slightly more tricky...)
Known issues:
- `Error: secret “nomad-keycloak-password” not found`: Right now the secret has been defined manually for a specific namespaceAdam FeketeAdam Feketehttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/886Link between NOMAD OASIS and NOMAD Central2023-12-21T16:05:24ZFelix DietrichLink between NOMAD OASIS and NOMAD Central## General
Currently every OASIS is just a clone of the central repository.
They are not linked together, not even through simple pings.
In addition to simple links, it is necessary to define how OASES can differ from the central instal...## General
Currently every OASIS is just a clone of the central repository.
They are not linked together, not even through simple pings.
In addition to simple links, it is necessary to define how OASES can differ from the central installation (in their version, their data, their user rights, ...).
This may be communicated to central, too. In this issue, we outline these challenges and provide a road map for implementation and discussion.
## Current GIT Issues related to OASIS (2022-05-24)
* Improve oasis synchronisation functionality #585
* Integrating NORTH into OASIS #825
* Oasis installation and registration #820
* NOMAD Oasis (GUI) #784
* NOMAD Oasis UX Test: user roles #757
## Requirements: LINK
* Use case 1: Send telemetry data to central in regular intervals. This is discussed in {## Requirements: Telemetry}
* Use-case 2: send data buckets + metadata. This is discussed in section {## Requirements: Data LINK}
## Requirements: Telemetry
* Which data should be sent?
* Users registered
* Data uploaded, stored
* Number of searches
* OASIS location
* Do we need fine-grained info about site-access? This may be a security/leak risk that some may not like.
* See #820
## Requirements: Soft constraints / Installation
* Central: be careful with DDOS attacks from "too many / malicious OASIS links"
* LINK is opt-out, enabled by default
* OASIS owners can disable LINK in a config
* See roles, #757
* The fact that each OASIS sends telemetry data by default MUST be communicated clearly, also how to disable it
* We must be careful with "user data processing" requirements (GDPR). Aggregated data should be fine, but maybe some telemetry data can be used to identify users (link clicks, etc.).
## Requirements: Data LINK
* Also called "Synchronization"
* Send data buckets
* Send metaschema information, when they are stored in files
* How to send new metaschemas defined in python? Not send at all?
* Versioning of data: what if metaschema in the OASIS is newer/older than the one in central?
* See #784
* See #585Daniel LehmbergDaniel Lehmberghttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/995Mail delivery failed: returning message to sender2023-12-21T15:39:05ZAdam FeketeMail delivery failed: returning message to senderit looks like all the emails that should got to the specific users ends up in support@nomad-lab.hu (and in my spam folder)
For example:
```
Mail Delivery System <Mailer-Daemon@www153.your-server.de>
A message that you sent could not b...it looks like all the emails that should got to the specific users ends up in support@nomad-lab.hu (and in my spam folder)
For example:
```
Mail Delivery System <Mailer-Daemon@www153.your-server.de>
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
lauri.himanen@gmail.com
(ultimately generated from support@nomad-lab.eu)
host gmail-smtp-in.l.google.com [142.251.5.27]
SMTP error from remote mail server after pipelined end of data:
550-5.7.1 [213.133.104.153] Messages missing a valid messageId header are not
550 5.7.1 accepted. t1-20020adfe101000000b0021f157ae467si6385629wrz.115 - gsmtp
---------- Forwarded message ----------
From: support@nomad-lab.eu
To: Lauri Himanen
Cc: The nomad team <support@nomad-lab.eu>
Bcc:
Date:
Subject: Processing completed
Dear Lauri Himanen,
your data uploaded at 2022-08-23T11:36:32.722000 has completed processing. You can review your data on your upload page: https://nomad-lab.eu/prod/v1/staging/gui/uploads
If you encounter any issues with your upload, please let us know and reply to this email.
The nomad team
```https://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1211minor fixes for the pipeline2022-12-02T23:09:04ZAdam Feketeminor fixes for the pipelinehttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1084Mix nomad.yaml based north config with user based hub config2023-12-21T15:38:45ZMarkus ScheidgenMix nomad.yaml based north config with user based hub configWe provide some configuration to JupyterHub based on settings in our `nomad.yaml`. This configuration also connects JupyterHUB to our UI, user-management, mounts volumes, etc.
We should still provide a way for Oasis admins to add more ...We provide some configuration to JupyterHub based on settings in our `nomad.yaml`. This configuration also connects JupyterHUB to our UI, user-management, mounts volumes, etc.
We should still provide a way for Oasis admins to add more configuration to JupyterHUB.
Either of those?
- Maybe two configs can be merged somehow and we allow users to mount their own JupyterHUB config.
- A dict-valued key in `nomad.yaml` that we pass to JupyterHUB via nomad's jupyterconfig.https://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1526Mongo and elasticsearch authentication2023-08-24T11:10:58ZMarkus ScheidgenMongo and elasticsearch authenticationWe should allow to use NOMAD with mongo and elastic that have security on.We should allow to use NOMAD with mongo and elastic that have security on.Markus ScheidgenMarkus Scheidgenhttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/757NOMAD Oasis UX Test: user roles2024-01-09T14:00:27ZFelix DietrichNOMAD Oasis UX Test: user rolesRelated to #756.
What people/roles are involved when a NOMAD Oasis is installed?
A person involved with the Oasis should be in one or multiple of the following roles:
- Oasis Owner
- Oasis Admin
- It Admin
- Data Producer
- Data C...Related to #756.
What people/roles are involved when a NOMAD Oasis is installed?
A person involved with the Oasis should be in one or multiple of the following roles:
- Oasis Owner
- Oasis Admin
- It Admin
- Data Producer
- Data Consumer
Oasis Owner:
- Responsible for the Oasis
- Usually professor, post-doc, lab owner...
- Decides to create the Oasis
- All general decisions are made by them
- Represents Oasis to the outside world
Oasis Admin:
- Can be the Owner or a delegated person (PhD candidate, post-doc, ...)
- Deals with more technical day-to-day issues
- Handles user management issues (from global keycloak repository? local users?)
- Plans and executes the setup of the IT infrastructure together with IT Admins
- Interacts with all other roles (Owner, IT, Producer, Consumer)
- Main contact person for users and for main NOMAD team regarding technical issues
IT Admin:
- Responsible for providing the technical infrastructure
- Setting up the server + providing hostname
- Setting up the installation of NOMAD (alternative: Oasis Admin?)
- Creates means for access restriction (VPN? HTTPS?)
Data Producer:
- Material Scientist who performs experiments and collects data
- Collects and prepares/sanitizes data
- Uploads data to the NOMA Oasis
- Decides on Access restrictions
- Potentially publishes the data to central NOMAD instance
Data Consumer:
- Scientist or Data Analyst or other end user of the materials science data
- Has read access to the data stored in the Oasis
- Downloads and analyzes data
- Compares different data items
- Visualizes dataFelix DietrichFelix Dietrichhttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1358North fiji tool crashing at stratup2023-02-23T11:08:01ZAdam FeketeNorth fiji tool crashing at stratupAdam FeketeAdam Feketehttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1360North/gui: Allow custom tools.json for deployments2023-05-17T13:17:44ZFlorian DobenerNorth/gui: Allow custom tools.json for deploymentsIt would be good to allow custom tools.json files for deployments. It is possible to mount a custom `tools.json` to change the properties of existing containers. However, the changes are only picked up by jupyter hub and not by the gui a...It would be good to allow custom tools.json files for deployments. It is possible to mount a custom `tools.json` to change the properties of existing containers. However, the changes are only picked up by jupyter hub and not by the gui as the `northTools.json` is compiled into the gui js. Therefore, it's not possible to add or remove containers in a deployment.https://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1347NORTH: the updated tool image has not been updated on the deployment2023-02-21T12:53:53ZAdam FeketeNORTH: the updated tool image has not been updated on the deploymentAdam FeketeAdam Feketehttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1345NORTH: Websocket connection (webtop based tools) failure on Nginx reverse proxy2023-02-16T15:51:11ZAdam FeketeNORTH: Websocket connection (webtop based tools) failure on Nginx reverse proxyhttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1404Operatin Nomad Oasis, manage Rabbitmq storage2023-12-21T15:38:53ZMichael GötteOperatin Nomad Oasis, manage Rabbitmq storageHey Nomad,
I am running a nomad oasis and for some reason rabbitmq has docker volumes with 33GB, that does not seem to be reasonable to me. If this grows in a similar rate it quickly becomes too big.
Here you see what i mean.
![image](...Hey Nomad,
I am running a nomad oasis and for some reason rabbitmq has docker volumes with 33GB, that does not seem to be reasonable to me. If this grows in a similar rate it quickly becomes too big.
Here you see what i mean.
![image](/uploads/9dd36d90a3520b557c4cf1a0619b84fb/image.png)
Do you have an idea what to do?
Best MichaMarkus ScheidgenMarkus Scheidgenhttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1008Plugin mechanism2023-12-21T16:06:49ZMichael GöttePlugin mechanismOasis administrators need to add more functionality to NOMAD without requiring a new image.
NOMAD develops want to separate non core functionality from the nomad-FAIR codebase and NOMAD images.
Potential functionality that can be added...Oasis administrators need to add more functionality to NOMAD without requiring a new image.
NOMAD develops want to separate non core functionality from the nomad-FAIR codebase and NOMAD images.
Potential functionality that can be added via plugins:
- schemas
- parsers
- normalisers
- APIs
- CLI commands
--
The original report by Micha: *Loading individual ELN code into an existing docker image*
Hey all,
this is a feature request. Imagine you want to use a fresh and tested docker image from your gitlab registry but you are not happy with the ELN normalizers in that image. Is it possible to develop and commit the ELN part in a different git project and then load this into the image of the registry?
An idea would be to do this in the ```docker-compose```file, e.g. add:
```
volumes:
- ./configs/nomad.yaml:/app/nomad.yaml
- ./eln/:/app/nomad/datamodel/metainfo/eln/
```
I will test this and let you know!
Best Michahttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1186Possible improvements on python packaging2023-12-21T16:06:49ZAdam FeketePossible improvements on python packaging- [ ] using src layout
- [ ] ease (>=) on package dependencies in the submodules and constrain them in the main (~=)
- [ ] python version ?? 3.10 or 3.11 (local oasis)
- [ ] test matrix ?
- [ ] convert parsers into plugins/extensions ...- [ ] using src layout
- [ ] ease (>=) on package dependencies in the submodules and constrain them in the main (~=)
- [ ] python version ?? 3.10 or 3.11 (local oasis)
- [ ] test matrix ?
- [ ] convert parsers into plugins/extensions VS monolithic package (Distribution package VS individual packages)
- [ ] implicit namespaces
```python
/src/nomad_lab/parser
/src/nomad_lab/gui
import nomad_lab.parser
import nomad_lab.gui
```
- [ ] linting: we might ignoring too much warnings (ignore them in the code instead)
alternative: black
- [ ] run `gui` and `jupyterhub` independently
- gui: is an independent application which depends on some artefacts
- [ ] adding `linter` and `pytest` configs to `myproject.toml`
- [ ] examples: storing examples in a separate repository using [git LFS](https://docs.gitlab.com/ee/topics/git/lfs/) for the zipped files like: https://gitlab.mpcdf.mpg.de/nomad-lab/nomad-fair-examples
- [ ] docs: The "compiled" documentation should not be part of the python source distribution. Reasoning:
* we need the nomad package to build the documentation which actually should also contain the documentation... Currently the only way to build the python sdist by building it twice.
* most of the other links on the gui are also pointing to external link
* the link of the logo of the documentation redirect to a another page (central deployment) and not to the one where it was actually deployed.https://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1631Publishing fails due to IndexError2023-08-16T11:40:26ZJoseph RudzinskiPublishing fails due to IndexErrorI am working to publish a dataset of molecular dynamics simulations (datsetid: k0FIIN93TDqcDatfaBWpXQ, not yet published) and recently made a series of somewhat large uploads (not exceeding the 30GB limit, but lots of entries, ~180 per u...I am working to publish a dataset of molecular dynamics simulations (datsetid: k0FIIN93TDqcDatfaBWpXQ, not yet published) and recently made a series of somewhat large uploads (not exceeding the 30GB limit, but lots of entries, ~180 per upload, which take a long time to process). Because of this, I worked with @mscheidg to make these uploads. This was done in the following way:
1. I stored my zip files on the nomad mpcdf computer and used the administrator option "local_path" with the "uploads" Post API endpoint.
2. I used a specialized deployment to make the upload at `https://nomad-lab.eu/prod/v1/util/`
3. The maximum allowed uploads for my account was extended
4. After the uploads were successful (all uploads and entries were parsed successfully except for one outlier entry in a single upload), I used the API to edit the Metadata of each upload.
Now, when I try to publish any of the uploads, either via API or in the GUI. I get the following error message: "Process publish_upload failed: IndexError: index out of range". See, e.g., uploadids: tgzOKVOfRNSCmHprfXnOaA, rOL3BcUrS6CdFjtBTN6NEQ.
On the upload page itself, on top of the entries it says: "Processing failed IndexError: index out of range, 180/180 entries processed". Could it be that there is a maximum number of entries per upload? Or could it have to do with my number of non-published uploads exceeding the normal limit?
I am not sure how to obtain any other information about the problem, since all the entries seemed to process without issues, so there is no relevant log information inside the entries. Is there a way to access logs for the upload?Markus ScheidgenMarkus Scheidgenhttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1230quick fix: initialise all git submodules during setup process2022-12-13T11:26:17ZAdam Feketequick fix: initialise all git submodules during setup processAdam FeketeAdam Feketehttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/991Random failing issues during the `gui tests`2022-09-13T08:18:04ZAdam FeketeRandom failing issues during the `gui tests`Quite regularly the gui test fails. As a workaround, we can restart the job and hope it will pass.
Here is the summary of a [failed test](https://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/jobs/1799899):
```
Summary of all failing tests
...Quite regularly the gui test fails. As a workaround, we can restart the job and hope it will pass.
Here is the summary of a [failed test](https://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/jobs/1799899):
```
Summary of all failing tests
FAIL src/components/uploads/UploadPage.spec.js (354.586 s)
● Delete selected entries from table
thrown: "Exceeded timeout of 120000 ms for a test.
Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."
252 | })
253 |
> 254 | test('Delete selected entries from table', async () => {
| ^
255 | await startAPI('tests.states.uploads.multiple_entries', 'tests/data/uploads/delete_entries_from_table', 'test', 'password')
256 | render(<UploadPage uploadId="dft_upload_1"/>)
257 |
at Object.<anonymous> (src/components/uploads/UploadPage.spec.js:254:1)
Test Suites: 1 failed, 25 passed, 26 total
Tests: 1 failed, 285 passed, 286 total
Snapshots: 0 total
Time: 2822.837 s
error Command failed with exit code 1.
```
There is another error message earlier in the log which might be the source of the actual problem:
```
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
```
Note: The tests' running time (54 minutes 1 second) is actually very close to the hard timeout limit (1h)Adam FeketeAdam Fekete