Developer Advanced Quiz

fcm conflicts|cf, denoted by the "C" after running fcm status, can be used to resolve which type(s) of conflicts?
1. tree only
2. text only
3. tree and text
C
fcm resolve always takes the form:
1. fcm resolve --accept working <FILENAME>
2. fcm resolve working <FILENAME>
3. fcm resolve -accept working <FILENAME>
4. fcm resolve --accept <FILENAME>
B

text conflicts are returned in the fcm status by:

```
C    src/module/hello_constants.py
```
```
   C src/module/hello_num.py
```
```
 M      .
```
```
?       src/module/hello.py
```

tree conflicts are returned in the fcm status by:

```
C    src/module/hello_constants.py
```
```
   C src/module/hello_num.py
```
```
 M      .
```
```
?       src/module/hello.py
```

When you add a rose stem test what commands must you run to check it?
1. rose app-upgrade -M /path/to/the/metadata/for/testing/ app/fcm_make HEAD && rose macro --fix -M /path/to/the/metadata/for/testing/; ./bin/upgrade_jules_test_apps vn#.#_t###
2. rose app-upgrade -M /path/to/the/metadata app/fcm_make <version> && rose macro --fix -M /path/to/the/metadata; ./bin/upgrade_jules_test_apps vn#.#_t###
3. rose app-upgrade -M /path/to/the/metadata/for/testing/ app/fcm_make && rose macro --fix -M /path/to/the/metadata/for/testing/; ./bin/upgrade_jules_test_apps vn#.#_t###
4. rose app-upgrade -M /path/to/the/metadata/for/testing/ app/fcm_make <version> && rose macro --fix -M /path/to/the/metadata/for/testing/; ./bin/upgrade_jules_test_apps vn#.#_t###
B
When adding a new rose-stem test what file(s) are to added/updated?
1. rose-stem/include/*/runtime*.rc and /graph*.rc
2. rose-stem/include/*/runtime*.rc and /graph*.rc and rose-stem/app/<NEW_ROSE_STEM_TEST_NAME>/rose-app.conf
3. rose-stem/include/*/runtime*.rc and rose-stem/app/<NEW_ROSE_STEM_TEST_NAME>/rose-app.conf
4. rose-stem/include/*/graph*.rc and rose-stem/app/<NEW_ROSE_STEM_TEST_NAME>/rose-app.conf
5. rose-stem/app/<NEW_ROSE_STEM_TEST_NAME>/rose-app.conf
B
Where can you find out what the latest vnX.X_txxx number is for running the app upgrade macro?
1. rose-meta/jules-fcm-make/versions.py
2. rose-meta/jules-standalone/versionXX_YY.py
3. rose-meta/jules-standalone/HEAD/rose-meta.conf
4. rose-meta/jules-standalone/versions.py
D
How can we create new KGO?
1. rose stem --group=all -S HOUSEKEEP=true --new<
2. rose stem --group=all -S HOUSEKEEPING=true --new<
3. rose stem --group=all -S HOUSEKEEP=false --new<
4. rose stem --group=all -S HOUSEKEEPING=false --new
D
To what file to do add an app upgrade macro?
1. rose-meta/jules-fcm-make/versions.py
2. rose-meta/jules-standalone/versionXX_YY.py
3. rose-meta/jules-standalone/HEAD/rose-meta.conf
4. rose-meta/jules-standalone/versions.py
D
What command would create a test branch for testing an upgrade macro?
1. fcm bc -k <ticket> --bob -t test <test_branch_name> fcm:jules.x_br/dev/<user>/<dev_branch_name>
2. fcm bc -k <ticket> --bob -t test fcm:jules.x_br/dev/<user>/<dev_branch_name>
3. fcm bc -k <ticket> --bob <test_branch_name> fcm:jules.x_br/dev/<user>/<dev_branch_name>
4. fcm bc -k <ticket> --bob <test_branch_name>
A
What command would you run to test and apply an app upgrade macro?
1. ./bin/upgrade_jules_apps -a
2. ./bin/upgrade_jules_test_apps
3. ./bin/upgrade_jules_test_apps vnX.X_txxx
4. ./bin/upgrade_jules_apps vnX.X_txxx
5. ./bin/upgrade_jules_apps -a
C
What do you need to do to check a change to an upgrade macro?
1. run rose-stem, check the diff using fcm diff -g, check rose edit Check fail-if, warn-if and Auto-fix
2. run rose-stem, check the diff using fcm diff -g
3. run rose-stem, check rose edit Check fail-if, warn-if and Auto-fix
4. check the diff using fcm diff -g
5. check the diff using fcm diff -g, check rose edit Check fail-if, warn-if and Auto-fix
6. check rose edit Check fail-if, warn-if and Auto-fix
A
If you have UM access, how can you checkout the UM code at vn#.#?
1. fcm co fcm:um.x_tr@rvn#.#
2. fcm co fcm:um.x_tr@#.#
3. fcm co fcm:um.x_tr@vn#.#
4. fcm co fcm:um.x_tr
5. fcm co fcm:um.x_tr@HEAD
C
What command would run the rose-stem tests for UM-JULES combined from the UM trunk directory?
1. rose stem --group=jules,developer --new
2. rose stem --group=jules,developer --new --source=.
3. rose stem --new --source=. --source=/path/to/jules/code
4. rose stem --group=jules,developer --new --source=. --source=/path/to/jules/code
D
What science/tech changes need a documentation change?
1. New science, new switch, changes to science
2. New science, new dimension, new switch, changes to science
3. New dimension, new switch, changes to science
4. New science, new dimension, new switch, changes to science, coding style changes
B
What the are coding standards often currently referred to as?
1. JULESDP3
2. UMDP3
3. DP3
B
When is a new rose-stem test required?
1. New science, if one does not already exist to safe guard science
2. For every change
3. New science only
4. Only if one does not already exist to safe guard science
A
How do can you compile and check the documentation branch from within docs/user_guide?
1. make latexpdf; evince build/latex/JULES_Users_Guide.pdf
2. make html; firefox build/html/index.html
3. make html; firefox build/html/index.html; make latexpdf; evince build/latex/JULES_Users_Guide.pdf
4. make html; make latexpdf
C
How can a documentation branch be created?
1. fcm bc <DOC_BRANCH_NAME> fcm:jules.doc.x_tr@vn#.#
2. fcm bc <DOC_BRANCH_NAME>
3. fcm bc fcm:jules_doc.x_tr@vn#.#
4. fcm bc <DOC_BRANCH_NAME> fcm:jules_doc.x_tr@vn#.#
D
For a documentation only ticket what tests need to be run??
1. Compile and check the html, LaTeX files
2. Compile and check the html, LaTeX files and rose-stem
3. Rose stem
A

JULES Developer Advanced quiz

JULES questions

Developer Advanced quiz

Answers